Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).analyze priority priority { all | category category | x-category string } action { allow | content-insert content_string | discard | redirect-url url | terminate-flow | www-reply-code-and-terminate-flow reply_code } [ edr edr_format_name ]
no analyze priority priority
analyze priority priority { all | category category | x-category string } action { allow | content-insert content_string | discard | redirect-url url | terminate-flow | www-reply-code-and-terminate-flow reply_code } [ reporting-edr reporting_edr_format_name ]
no analyze priority priority
priority priority
priority must be an integer from 1 to 65535 that is unique in the content filtering policy.
category category
category must be one of the following.
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
Important: Content can simultaneously match multiple categories, therefore specific priority must be used for required evaluation precedence.x-category string
string specifies the unclassified category to be rated, and must be an alphanumeric string of 1 through 6 characters.
action { allow | content-insert content_string | discard | redirect-url url | terminate-flow | www-reply-code-and-terminate-flow reply_code }
allow: With static content filtering, this option allows the request for content. In dynamic content filtering it allows the content itself.
content-insert content_string: Specifies the content string to be inserted in place of the message returned from prohibited/restricted site or content server.
For static content filtering, content_string is used to create a response to the subscriber’s attempt to get content. In dynamic content filtering, it is used to replace the content returned by a server.
content_string must be an alphanumeric string of 1 through 1023 characters.
discard: For static content filtering, this option discards the packet(s) that requested. In dynamic content filtering, it discards the packet(s) that contain(s) the content.
redirect-url url: Redirects the subscriber to the specified URL.
url must be an alphanumeric string of 1 through 1023 characters in the http://search.com/subtarg=#HTTP.URL# format.
terminate-flow: Terminates the TCP connection gracefully between the subscriber and server, and sends a TCP FIN to the subscriber and a TCP RST to the server.
www-reply-code-and-terminate-flow reply_code: Terminates the flow with the specified reply code. reply_code must be a reply code that is an integer from 100 through 599.
Important: Static-and-Dynamic Content Filtering is only supported in 9.0 and later releases.edr edr_format_name
Important: This option is applicable only to 12.1 and earlier releases. In 12.2 and later releases, it is deprecated and replaced by the reporting-edr option.edr_format_name is the name of a pre-defined EDR file format name in the EDR Format Configuration Mode, and must be an alphanumeric string of 1 through 63 characters.
Important: EDRs generated through this keyword are different from charging EDRs generated for subscriber accounting and billing. For more information on generation of charging EDRs, refer to the ACS Rulebase Configuration Mode Commands chapter.reporting-edr reporting_edr_format_name
Important: This option is available only in 12.2 and later releases.reporting_edr_format_name must be an alphanumeric string of 1 through 63 characters.
discarded-flow-content-id content_id
A flow end-condition EDR would be generated as a charging EDR for content-filtered packets. No billing EDRs (even with flow-end) would be generated for a discarded packet as the flow will not end. Dual EDRs would exist for customers who want to use “flow end” to get EDRs for charging, plus CF-specific EDRs. The second EDR for charging comes from the flow end-condition content-filtering configuration in the Rulebase Configuration Mode.
The discarded-flow-content-id configuration can be used for accumulating statistics for UDR generation in case CF discards the packets. These statistics for UDR generation (based on the CF content ID) would also be accumulated in case of ACS error scenarios where the packets are discarded but the flow does not end.
If, in the Rulebase Configuration Mode, the content-filtering flow-any-error configuration is set to deny, then all the denied packets will be accounted for by the discarded-flow-content-id config. That is, the content_id will be used to generate UDRs for the denied packets in case of content filtering.
failure-action { allow | content-insert content_string | discard | redirect-url url | terminate-flow | www-reply-code-and-terminate-flow reply_code } [ edr edr_format_name ]
Important: Static-and-Dynamic Content Filtering is only supported in 9.0 and later releases.content-insertion content_string
For content filtering, the content_string is used to create a response to the subscriber’s attempt to get content. In dynamic content filtering it replaces the content returned by a server.
content_string is an alphanumeric string of 1 through 1023 characters.
Important: Static-and-Dynamic Content Filtering is only supported in 9.0 and later releases.
Important: Static-and-Dynamic Content Filtering is only supported in 9.0 and later releases.redirect-url url
url must be an alphanumeric string of 1 through 1023 characters, in the following format: http://search.com/subtarg=#HTTP.URL#
www-reply-code-and-terminate-flow reply_code
edr edr_format_name
Use this command to set the failure action to take when no content filtering analysis result is available to analyze for analyze priority priority category category_string command.
